Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Experiment: Memory/thread-safe runtime #1276

Closed
wants to merge 1 commit into from
Closed

Experiment: Memory/thread-safe runtime #1276

wants to merge 1 commit into from

Conversation

dcodeIO
Copy link
Member

@dcodeIO dcodeIO commented May 15, 2020

Another experiment, this time to make the runtime memory and thread-safe. So far this should be memory-safe in that multiple modules can share the memory allocator and garbage collector, but there's no locking in place yet. As-is, stuff will explode.

This will most likely not be a viable approach in the long term due to all the locking overhead it ultimately introduces, but perhaps it can serve as the start of a filler implementation until there's something better. Regarding something better, I imagine a global allocator distributing pages to threads which then manage their memory with TLSF or otherwise. We also all know that manual locking is error-prone, and something more aligned with JS, like backed by workers and postMessage, would be much safer.

@dcodeIO
Copy link
Member Author

dcodeIO commented May 16, 2020

Keeping this PR open as part of 2020 vacuum, as it is fairly fresh.

@dcodeIO dcodeIO marked this pull request as draft May 16, 2020 18:04
@dcodeIO dcodeIO removed the vacuumed label May 28, 2020
@HerrCai0907
Copy link
Member

clean outdated draft PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants